Migrating to HTTPS

Overview

With the changes to the Chrome browser, cookies are not being shared across web sites or web application domains unless otherwise specified. Though these changes have been updated by Algonomy, the Chrome update also requires HTTPS to share cookies across domains. The following lists the changes needed to move to HTTPS with Algonomy.

• Update the ‘Site URL’ in the Personalization Dashboard. https://portal.richrelevance.com/rrportal/siteConfig.jsp

• If the RR feed contains absolute URL's, these must be updated to use https.

• Links used in Engage content must be updated to https.

• Make sure all request to RR use https.

• Client site integration

• p13n library inclusion

• Ensure all calls use https, or take the protocol from the current page.

• https://help.richrelevance.com/Integration_Guide/0010_JSON_Integration%3A_Core_Integration

• Server-side integration – Recommend, Discover

• Make the request using https, to get https links in the response.

• https://help.richrelevance.com/3_Recommend/Recommend%3A_APIs/recsForPlacements

• Server-side integration – Find

• Include the parameter ssl=true, to get https links in the response.

• https://help.richrelevance.com/Find/Find_API/0001_Find%3A_Search_API

• Server side integration – Engage

• Include the parameter ssl=true, to get https links in the response.

• https://help.richrelevance.com/Relevance_Cloud/Relevance_Cloud%3A_Core_APIs/Core_APIs/Personalize_API

• Let Algonomy know when you are making these changes as we will need to make sure that there are no customizations made for you in the javascript response that need updating to https